home *** CD-ROM | disk | FTP | other *** search
- This directory contains Linux 1.3.x (a.out) executables for XEmacs
- 19.13. These were compiled with Motif 2.0, X11R6, XPM, X-Face, -m486
- -O optimization, and have all libraries statically linked.
-
- Built by William Perry (wmperry@spry.com)
-
- The tar file which contains these executables contains only the
- executables (the architecture-dependent files.) To use these
- executables, you will also need the architecture-independent files
- (the `lisp', `etc' and `info' directories.) These files are
- distributed in a seperate file (xemacs-19.13-common.tar.gz.)
-
- HOW TO INSTALL
- ==============
-
- Simply cd to the directory in which you wish to install xemacs,
- and then unpack the architecture independent tar file, followed by
- the architecture-dependent files for those architectures you use.
-
- cd /usr/local/ # or wherever you install 3rd-party software
- gzip -dc xemacs-19.13-common.tar.gz | tar -pxf -
- gzip -dc xemacs-19.13-i486-unknown-linuxaout-motif.tar.gz | tar -pxf -
-
- Replace `/usr/local/' with what you like, but it probably ought not
- have `xemacs' or a version number in it - that directory is expected
- to be the common prefix for installed software, and xemacs-specific
- subdirectories of it will be created. The directories are arranged
- in such a way that multiple versions of xemacs can peaceably coexist
- under the same `/usr/local/' tree.
-
- After unpacking, you will have a directory structure like:
-
- ./bin/i486-unknown-linuxaout1.3.21/xemacs-19.13* executable
- ./lib/xemacs-19.13/lisp/ lisp library
- ./lib/xemacs-19.13/etc/ data directory
- ./lib/xemacs-19.13/info/ documentation
- ./lib/xemacs-19.13/i486-unknown-linuxaout1.3.21/ utility programs
- ./lib/xemacs/lock/ lock directory
- ./lib/xemacs/site-lisp/ local lisp code
-
- For the executable to work, the directory layout must look pretty
- much like this; the executable looks for "sibling" directories at
- run-time to figure out where its lisp library is. These constraints
- on the local directory layout are necessary to avoid having to
- hardcode pathnames into the executables, or require that environment
- variables be set before running the executable.
-
- It is possible to do a multi-architecture in such a way that the
- executables for the various architectures are on different
- partitions; in that case you must install some symbolic links so
- that the directory structure appears as above from the clients.
-
- For example, assume that $LOCAL refers to a directory which is
- mounted only on machines of the same type; and $SHARED refers to
- a directory which is shared among all machines. You could set up
- the directory hierarchy like this:
-
- $LOCAL/bin/xemacs-19.13*
- $LOCAL/lib/xemacs-19.13/i486-unknown-linuxaout1.3.21/
- $LOCAL/lib/xemacs-19.13/lisp@ -> $SHARED/xemacs-19.13/lisp/
- $LOCAL/lib/xemacs-19.13/etc@ -> $SHARED/xemacs-19.13/etc/
- $LOCAL/lib/xemacs-19.13/info@ -> $SHARED/xemacs-19.13/info/
- $LOCAL/lib/xemacs@ -> $SHARED/xemacs/
-
- $SHARED/xemacs-19.13/lisp/
- $SHARED/xemacs-19.13/etc/
- $SHARED/xemacs-19.13/info/
- $SHARED/xemacs/lock/
- $SHARED/xemacs/site-lisp/
-
- That is, the various $SHARED directories contain only the
- architecture-independent files, but still look like normal
- installation trees, since the architecture-independent
- directories have been replaced with symbolic links to the
- single $COMMON tree.
-